Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(doc): support additional info from label/annotations #21

Closed
wants to merge 1 commit into from

Conversation

djetelina
Copy link
Contributor

This design proposal talks about how to extend the OpenSLO spec with some very useful information, which can be used in dashboards (again) or by platforms like Backstage (surprise).

If you think of any more important/interesting fields, please say so :)

This design proposal talks about how to extend the OpenSLO spec with some very useful information, which can be used in dashboards (again) or by platforms like Backstage (surprise).

If you think of any more important/interesting fields, please say so :)

Signed-off-by: David Jetelina <[email protected]>
@fourstepper
Copy link
Contributor

I just approved this, but why is this under docs/ when it could probably be an adr?

@djetelina
Copy link
Contributor Author

I just approved this, but why is this under docs/ when it could probably be an adr?

Well, it didn't feel like an ADR, or rather I didn't know how to word it as an ADR. I'm happy to rework it, suggestions are welcome.

@fourstepper
Copy link
Contributor

Looking at this with fresher eyes, I'm going to close this one. I think that this doesn't have to be part of osko at all, rather it's some organization-specific convention that may and will differ from org to org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants